Bazaar

Hi Lars,

In tajik bazaar is market. When you talk of bazaar outside of bazaar it means haos. When someone does things wrong, other may correct him: "hei, you are not in bazaar, behave as respected". Now I am in bazaar. Please suggest corrections.
I got my code from repository as branch. I didn't commit since then i guess. I made changes on poms, created struts2 test modules, implemented 'easy help' and 'datavalue history' functionalities. What to do now? commit all in one? where does it go? I could't find anywhere with my login on launchpad saying my branch. I also want to version my changes. I cannot continue with so many changes not versioned.
Easy help functionality is fine to go (simply action file and vm), but datavalue history brings many changes starting from new dependencies and existing code change to introduce @annotations for hibernate. DataValue entity, which has composite primary key refering to foreign key to other for entities (defined in hbm.xml) had been slightly changed (now annotated), services to it as well. Also one dependency is not on maven2 repo, it is not there as latest (olders are there though), needs to be manually set. This is enver library by jboss, to be part of hibernate 3.5 fairly soon as they promise.
For easy help we need also someone who is good in manual writing to place tags where necessary (other web modules menu.vm or anywhere control needs help) and provide en_GB.properties strings acordingly. These changes later should be placed into trunk and translated into other languages. General Help menu could also use the same strings.

regards,
murod.

Hi Lars

I think Murod's point is a reflection of a wider problem we have
regarding project management. At least I don't feel I have yet got
completely on top of all the issues around bazaar management of
series, branches etc. I know I haven't dedicated as much time to it
as I might have. Mostly these are not bazaar problems. When you go
to a bazaar which you are familiar with it is a very productive
experience. Wondering around a bazaar which is new to you, well, you
can easily get lost.

I think it would be a good idea to maybe set a date (like next Friday)
for a core developers conference call - maybe using skype or something
similar. We can use the intervening week to study all the best
practices and discuss on list.

Meanwhile I guess Murod should commit his code into the sandbox. We
should always be able to commit code somewhere - rather than not
committing. Then you and others can look at it and decide whether
some or all of this goes into 2.02/2.03 etc. I guess this involves:

bzr co lp:~dhis2-devs/dhis2/sandbox
add the code in a new folder here and add the folder to bzr
bzr commit

Does this sound right?

Regards
Bob

···

2009/4/17 Murodullo Latifov <murodlatifov@yahoo.com>:

Hi Lars,

In tajik bazaar is market. When you talk of bazaar outside of bazaar it means haos. When someone does things wrong, other may correct him: "hei, you are not in bazaar, behave as respected". Now I am in bazaar. Please suggest corrections.
I got my code from repository as branch. I didn't commit since then i guess. I made changes on poms, created struts2 test modules, implemented 'easy help' and 'datavalue history' functionalities. What to do now? commit all in one? where does it go? I could't find anywhere with my login on launchpad saying my branch. I also want to version my changes. I cannot continue with so many changes not versioned.
Easy help functionality is fine to go (simply action file and vm), but datavalue history brings many changes starting from new dependencies and existing code change to introduce @annotations for hibernate. DataValue entity, which has composite primary key refering to foreign key to other for entities (defined in hbm.xml) had been slightly changed (now annotated), services to it as well. Also one dependency is not on maven2 repo, it is not there as latest (olders are there though), needs to be manually set. This is enver library by jboss, to be part of hibernate 3.5 fairly soon as they promise.
For easy help we need also someone who is good in manual writing to place tags where necessary (other web modules menu.vm or anywhere control needs help) and provide en_GB.properties strings acordingly. These changes later should be placed into trunk and translated into other languages. General Help menu could also use the same strings.

regards,
murod.

_______________________________________________
Mailing list: https://launchpad.net/~dhis2-devs
Post to : dhis2-devs@lists.launchpad.net
Unsubscribe : https://launchpad.net/~dhis2-devs
More help : https://help.launchpad.net/ListHelp

Hi people,

Yes, we should have skype conference regarding bazaar SCM with some online training. On blueprints I couldn't assign myself for implementing. Also both 'easy access help' and 'datavalue history' show 'branch exists', I couldn't get hold of them. Maybe I have not enough access rights? Or admin should assign it to? I am afraid to do exesive job of copy/paste after all. :slight_smile:
Can someone point me to proper documentation for bazaar users?

regards,
murod

···

----- Original Message ----
From: Bob Jolliffe <bobjolliffe@gmail.com>
To: Murodullo Latifov <murodlatifov@yahoo.com>
Cc: DHIS 2 developers <dhis2-devs@lists.launchpad.net>
Sent: Friday, April 17, 2009 11:57:45 AM
Subject: Re: [Dhis2-devs] Bazaar

Hi Lars

I think Murod's point is a reflection of a wider problem we have
regarding project management. At least I don't feel I have yet got
completely on top of all the issues around bazaar management of
series, branches etc. I know I haven't dedicated as much time to it
as I might have. Mostly these are not bazaar problems. When you go
to a bazaar which you are familiar with it is a very productive
experience. Wondering around a bazaar which is new to you, well, you
can easily get lost.

I think it would be a good idea to maybe set a date (like next Friday)
for a core developers conference call - maybe using skype or something
similar. We can use the intervening week to study all the best
practices and discuss on list.

Meanwhile I guess Murod should commit his code into the sandbox. We
should always be able to commit code somewhere - rather than not
committing. Then you and others can look at it and decide whether
some or all of this goes into 2.02/2.03 etc. I guess this involves:

bzr co lp:~dhis2-devs/dhis2/sandbox
add the code in a new folder here and add the folder to bzr
bzr commit

Does this sound right?

Regards
Bob

2009/4/17 Murodullo Latifov <murodlatifov@yahoo.com>:

Hi Lars,

In tajik bazaar is market. When you talk of bazaar outside of bazaar it means haos. When someone does things wrong, other may correct him: "hei, you are not in bazaar, behave as respected". Now I am in bazaar. Please suggest corrections.
I got my code from repository as branch. I didn't commit since then i guess. I made changes on poms, created struts2 test modules, implemented 'easy help' and 'datavalue history' functionalities. What to do now? commit all in one? where does it go? I could't find anywhere with my login on launchpad saying my branch. I also want to version my changes. I cannot continue with so many changes not versioned.
Easy help functionality is fine to go (simply action file and vm), but datavalue history brings many changes starting from new dependencies and existing code change to introduce @annotations for hibernate. DataValue entity, which has composite primary key refering to foreign key to other for entities (defined in hbm.xml) had been slightly changed (now annotated), services to it as well. Also one dependency is not on maven2 repo, it is not there as latest (olders are there though), needs to be manually set. This is enver library by jboss, to be part of hibernate 3.5 fairly soon as they promise.
For easy help we need also someone who is good in manual writing to place tags where necessary (other web modules menu.vm or anywhere control needs help) and provide en_GB.properties strings acordingly. These changes later should be placed into trunk and translated into other languages. General Help menu could also use the same strings.

regards,
murod.

_______________________________________________
Mailing list: https://launchpad.net/~dhis2-devs
Post to : dhis2-devs@lists.launchpad.net
Unsubscribe : https://launchpad.net/~dhis2-devs
More help : https://help.launchpad.net/ListHelp

http://doc.bazaar-vcs.org/bzr.dev/en/user-guide/index.html
and
http://doc.bazaar-vcs.org/bzr.dev/en/user-reference/bzr_man.html

are probably all the docs you should need… But the things you point out regrading blueprints has more to do with launchpad than bazaar. I have spent considerable amount of time studying distributed VCS including mercurial, bazaar, git and the rest… and have been raising this point from the dev conference.

All we need for Murod’s work is a branch of his features like a centralized VCS way… the core devs can then pull only those changes from murod’s branch, merge as local commits to trunk branch and then commit it back to the trunk. Managing conflicts shouldn’t be much issue, but understanding and testing the changes will surely be some effort.

···

Regards,
Saptarshi PURKAYASTHA
Director R & D, HISP India
Health Information Systems Programme

My Tech Blog: http://sunnytalkstech.blogspot.com

You Live by CHOICE, Not by CHANCE

2009/4/17 Murodullo Latifov murodlatifov@yahoo.com

Hi people,

Yes, we should have skype conference regarding bazaar SCM with some online training. On blueprints I couldn’t assign myself for implementing. Also both ‘easy access help’ and ‘datavalue history’ show ‘branch exists’, I couldn’t get hold of them. Maybe I have not enough access rights? Or admin should assign it to? I am afraid to do exesive job of copy/paste after all. :slight_smile:

Can someone point me to proper documentation for bazaar users?

regards,

murod

----- Original Message ----

From: Bob Jolliffe bobjolliffe@gmail.com

To: Murodullo Latifov murodlatifov@yahoo.com

Cc: DHIS 2 developers dhis2-devs@lists.launchpad.net

Sent: Friday, April 17, 2009 11:57:45 AM

Subject: Re: [Dhis2-devs] Bazaar

Hi Lars

I think Murod’s point is a reflection of a wider problem we have

regarding project management. At least I don’t feel I have yet got

completely on top of all the issues around bazaar management of

series, branches etc. I know I haven’t dedicated as much time to it

as I might have. Mostly these are not bazaar problems. When you go

to a bazaar which you are familiar with it is a very productive

experience. Wondering around a bazaar which is new to you, well, you

can easily get lost.

I think it would be a good idea to maybe set a date (like next Friday)

for a core developers conference call - maybe using skype or something

similar. We can use the intervening week to study all the best

practices and discuss on list.

Meanwhile I guess Murod should commit his code into the sandbox. We

should always be able to commit code somewhere - rather than not

committing. Then you and others can look at it and decide whether

some or all of this goes into 2.02/2.03 etc. I guess this involves:

bzr co lp:~dhis2-devs/dhis2/sandbox

add the code in a new folder here and add the folder to bzr

bzr commit

Does this sound right?

Regards

Bob

2009/4/17 Murodullo Latifov murodlatifov@yahoo.com:

Hi Lars,

In tajik bazaar is market. When you talk of bazaar outside of bazaar it means haos. When someone does things wrong, other may correct him: “hei, you are not in bazaar, behave as respected”. Now I am in bazaar. Please suggest corrections.

I got my code from repository as branch. I didn’t commit since then i guess. I made changes on poms, created struts2 test modules, implemented ‘easy help’ and ‘datavalue history’ functionalities. What to do now? commit all in one? where does it go? I could’t find anywhere with my login on launchpad saying my branch. I also want to version my changes. I cannot continue with so many changes not versioned.

Easy help functionality is fine to go (simply action file and vm), but datavalue history brings many changes starting from new dependencies and existing code change to introduce @annotations for hibernate. DataValue entity, which has composite primary key refering to foreign key to other for entities (defined in hbm.xml) had been slightly changed (now annotated), services to it as well. Also one dependency is not on maven2 repo, it is not there as latest (olders are there though), needs to be manually set. This is enver library by jboss, to be part of hibernate 3.5 fairly soon as they promise.

For easy help we need also someone who is good in manual writing to place tags where necessary (other web modules menu.vm or anywhere control needs help) and provide en_GB.properties strings acordingly. These changes later should be placed into trunk and translated into other languages. General Help menu could also use the same strings.

regards,

murod.


Mailing list: https://launchpad.net/~dhis2-devs

Post to : dhis2-devs@lists.launchpad.net

Unsubscribe : https://launchpad.net/~dhis2-devs

More help : https://help.launchpad.net/ListHelp


Mailing list: https://launchpad.net/~dhis2-devs

Post to : dhis2-devs@lists.launchpad.net

Unsubscribe : https://launchpad.net/~dhis2-devs

More help : https://help.launchpad.net/ListHelp

http://doc.bazaar-vcs.org/bzr.dev/en/user-guide/index.html
and
http://doc.bazaar-vcs.org/bzr.dev/en/user-reference/bzr_man.html

are probably all the docs you should need... But the things you point out
regrading blueprints has more to do with launchpad than bazaar. I have spent
considerable amount of time studying distributed VCS including mercurial,
bazaar, git and the rest... and have been raising this point from the dev
conference.

All we need for Murod's work is a branch of his features like a centralized
VCS way... the core devs can then pull only those changes from murod's
branch, merge as local commits to trunk branch and then commit it back to
the trunk. Managing conflicts shouldn't be much issue, but understanding and
testing the changes will surely be some effort.

Yes but the point is that it is no good if he just creates a personal
local branch which is what is mostly described in the documentation.
His branch must also be on launchpad. Which is why I suggested
perhaps putting it in (or next to) the sandbox which is owned by
dhis2-devs.

I guess alternatively you just make your own branch by going to
https://code.launchpad.net/~miri and creating the branch there. Then
the core devs decide how, when and what to merge with trunk.

Cheers
Bob

···

2009/4/17 Saptarshi Purkayastha <sunbiz@gmail.com>:

---
Regards,
Saptarshi PURKAYASTHA
Director R & D, HISP India
Health Information Systems Programme

My Tech Blog: http://sunnytalkstech.blogspot.com
You Live by CHOICE, Not by CHANCE

2009/4/17 Murodullo Latifov <murodlatifov@yahoo.com>

Hi people,

Yes, we should have skype conference regarding bazaar SCM with some online
training. On blueprints I couldn't assign myself for implementing. Also both
'easy access help' and 'datavalue history' show 'branch exists', I couldn't
get hold of them. Maybe I have not enough access rights? Or admin should
assign it to? I am afraid to do exesive job of copy/paste after all. :slight_smile:
Can someone point me to proper documentation for bazaar users?

regards,
murod

----- Original Message ----
From: Bob Jolliffe <bobjolliffe@gmail.com>
To: Murodullo Latifov <murodlatifov@yahoo.com>
Cc: DHIS 2 developers <dhis2-devs@lists.launchpad.net>
Sent: Friday, April 17, 2009 11:57:45 AM
Subject: Re: [Dhis2-devs] Bazaar

Hi Lars

I think Murod's point is a reflection of a wider problem we have
regarding project management. At least I don't feel I have yet got
completely on top of all the issues around bazaar management of
series, branches etc. I know I haven't dedicated as much time to it
as I might have. Mostly these are not bazaar problems. When you go
to a bazaar which you are familiar with it is a very productive
experience. Wondering around a bazaar which is new to you, well, you
can easily get lost.

I think it would be a good idea to maybe set a date (like next Friday)
for a core developers conference call - maybe using skype or something
similar. We can use the intervening week to study all the best
practices and discuss on list.

Meanwhile I guess Murod should commit his code into the sandbox. We
should always be able to commit code somewhere - rather than not
committing. Then you and others can look at it and decide whether
some or all of this goes into 2.02/2.03 etc. I guess this involves:

bzr co lp:~dhis2-devs/dhis2/sandbox
add the code in a new folder here and add the folder to bzr
bzr commit

Does this sound right?

Regards
Bob

2009/4/17 Murodullo Latifov <murodlatifov@yahoo.com>:
>
> Hi Lars,
>
> In tajik bazaar is market. When you talk of bazaar outside of bazaar it
> means haos. When someone does things wrong, other may correct him: "hei, you
> are not in bazaar, behave as respected". Now I am in bazaar. Please suggest
> corrections.
> I got my code from repository as branch. I didn't commit since then i
> guess. I made changes on poms, created struts2 test modules, implemented
> 'easy help' and 'datavalue history' functionalities. What to do now? commit
> all in one? where does it go? I could't find anywhere with my login on
> launchpad saying my branch. I also want to version my changes. I cannot
> continue with so many changes not versioned.
> Easy help functionality is fine to go (simply action file and vm), but
> datavalue history brings many changes starting from new dependencies and
> existing code change to introduce @annotations for hibernate. DataValue
> entity, which has composite primary key refering to foreign key to other for
> entities (defined in hbm.xml) had been slightly changed (now annotated),
> services to it as well. Also one dependency is not on maven2 repo, it is not
> there as latest (olders are there though), needs to be manually set. This is
> enver library by jboss, to be part of hibernate 3.5 fairly soon as they
> promise.
> For easy help we need also someone who is good in manual writing to
> place tags where necessary (other web modules menu.vm or anywhere control
> needs help) and provide en_GB.properties strings acordingly. These changes
> later should be placed into trunk and translated into other languages.
> General Help menu could also use the same strings.
>
> regards,
> murod.
>
>
>
>
>
> _______________________________________________
> Mailing list: https://launchpad.net/~dhis2-devs
> Post to : dhis2-devs@lists.launchpad.net
> Unsubscribe : https://launchpad.net/~dhis2-devs
> More help : https://help.launchpad.net/ListHelp
>

_______________________________________________
Mailing list: https://launchpad.net/~dhis2-devs
Post to : dhis2-devs@lists.launchpad.net
Unsubscribe : https://launchpad.net/~dhis2-devs
More help : https://help.launchpad.net/ListHelp

_______________________________________________
Mailing list: https://launchpad.net/~dhis2-devs
Post to : dhis2-devs@lists.launchpad.net
Unsubscribe : https://launchpad.net/~dhis2-devs
More help : https://help.launchpad.net/ListHelp

I guess alternatively you just make your own branch by going to

https://code.launchpad.net/~miri and creating the branch there. Then

the core devs decide how, when and what to merge with trunk.

The second part from you reply is exactly what I said… He should commit it to his branch (on lp) and then the core devs do the merge

···

Regards,
Saptarshi PURKAYASTHA
Director R & D, HISP India
Health Information Systems Programme

My Tech Blog: http://sunnytalkstech.blogspot.com

You Live by CHOICE, Not by CHANCE

2009/4/17 Murodullo Latifov murodlatifov@yahoo.com

Hi people,

Yes, we should have skype conference regarding bazaar SCM with some online

training. On blueprints I couldn’t assign myself for implementing. Also both

‘easy access help’ and ‘datavalue history’ show ‘branch exists’, I couldn’t

get hold of them. Maybe I have not enough access rights? Or admin should

assign it to? I am afraid to do exesive job of copy/paste after all. :slight_smile:

Can someone point me to proper documentation for bazaar users?

regards,

murod

----- Original Message ----

From: Bob Jolliffe bobjolliffe@gmail.com

To: Murodullo Latifov murodlatifov@yahoo.com

Cc: DHIS 2 developers dhis2-devs@lists.launchpad.net

Sent: Friday, April 17, 2009 11:57:45 AM

Subject: Re: [Dhis2-devs] Bazaar

Hi Lars

I think Murod’s point is a reflection of a wider problem we have

regarding project management. At least I don’t feel I have yet got

completely on top of all the issues around bazaar management of

series, branches etc. I know I haven’t dedicated as much time to it

as I might have. Mostly these are not bazaar problems. When you go

to a bazaar which you are familiar with it is a very productive

experience. Wondering around a bazaar which is new to you, well, you

can easily get lost.

I think it would be a good idea to maybe set a date (like next Friday)

for a core developers conference call - maybe using skype or something

similar. We can use the intervening week to study all the best

practices and discuss on list.

Meanwhile I guess Murod should commit his code into the sandbox. We

should always be able to commit code somewhere - rather than not

committing. Then you and others can look at it and decide whether

some or all of this goes into 2.02/2.03 etc. I guess this involves:

bzr co lp:~dhis2-devs/dhis2/sandbox

add the code in a new folder here and add the folder to bzr

bzr commit

Does this sound right?

Regards

Bob

2009/4/17 Murodullo Latifov murodlatifov@yahoo.com:

Hi Lars,

In tajik bazaar is market. When you talk of bazaar outside of bazaar it

means haos. When someone does things wrong, other may correct him: "hei, you

are not in bazaar, behave as respected". Now I am in bazaar. Please suggest

corrections.

I got my code from repository as branch. I didn’t commit since then i

guess. I made changes on poms, created struts2 test modules, implemented

‘easy help’ and ‘datavalue history’ functionalities. What to do now? commit

all in one? where does it go? I could’t find anywhere with my login on

launchpad saying my branch. I also want to version my changes. I cannot

continue with so many changes not versioned.

Easy help functionality is fine to go (simply action file and vm), but

datavalue history brings many changes starting from new dependencies and

existing code change to introduce @annotations for hibernate. DataValue

entity, which has composite primary key refering to foreign key to other for

entities (defined in hbm.xml) had been slightly changed (now annotated),

services to it as well. Also one dependency is not on maven2 repo, it is not

there as latest (olders are there though), needs to be manually set. This is

enver library by jboss, to be part of hibernate 3.5 fairly soon as they

promise.

For easy help we need also someone who is good in manual writing to

place tags where necessary (other web modules menu.vm or anywhere control

needs help) and provide en_GB.properties strings acordingly. These changes

later should be placed into trunk and translated into other languages.

General Help menu could also use the same strings.

regards,

murod.


Mailing list: https://launchpad.net/~dhis2-devs

Post to : dhis2-devs@lists.launchpad.net

Unsubscribe : https://launchpad.net/~dhis2-devs

More help : https://help.launchpad.net/ListHelp


Mailing list: https://launchpad.net/~dhis2-devs

Post to : dhis2-devs@lists.launchpad.net

Unsubscribe : https://launchpad.net/~dhis2-devs

More help : https://help.launchpad.net/ListHelp


Mailing list: https://launchpad.net/~dhis2-devs

Post to : dhis2-devs@lists.launchpad.net

Unsubscribe : https://launchpad.net/~dhis2-devs

More help : https://help.launchpad.net/ListHelp