Re: [translate-pootle] Release and development process - would value your input
az., 2013.eko marren 27a 15:56(e)an, Leandro Regueiro(e)k idatzi zuen: > On Wed, Mar 27, 2013 at 2:12 PM, Dwayne Bailey > wrote: > >> Branch naming >> >> 1. Previous - simply 2.5.0 - I think this then confuses tags and >> branches that have the same name >> 2. As written - 2.5.0-branch - I'm liking this less. >> 3. Suggested by Julen stable/2.5.0 > > I like 3. Or perhaps release/2.5.0. I think 'release/x.y.z' will be confusing if the branching happens before any actual release has happened. -- Own the Future-Intel(R) Level Up Game Demo Contest 2013 Rise to greatness in Intel's independent game demo contest. Compete for recognition, cash, and the chance to get your game on Steam. $5K grand prize plus 10 genre and skill prizes. Submit your demo by 6/6/13. http://altfarm.mediaplex.com/ad/ck/12124-176961-30367-2 ___ Translate-pootle mailing list Translate-pootle@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/translate-pootle
Re: [translate-pootle] Release and development process - would value your input
On Wed, Mar 27, 2013 at 2:12 PM, Dwayne Bailey wrote: > Hi, > > Julen and I met in Pretoria in January to discuss our release and > development process moving forward after 2.5. > > I've finally managed to capture that discussion and have updated the > release document here: > http://docs.translatehouse.org/projects/pootle/en/latest/developers/release.html > > Would love you all to give that a read and check for any typos and errors. > > In general the doc should give some clarity on: > >1. When you can contribute and land things >2. When to expect a new release of Pootle >3. What you can expect when running from master. > > > However, we do need some input and help in these two thing: > >1. When to branch when creating time-based releases. >2. What to name our branches. > > > When to branch > Options > >1. As written now branch would happen at the end of the stabilising >month, i.e. as late as possible - thus forcing focus on the stabalisation >2. Branch early and port change to the branch as needed - allows master >to continue in rapid development >3. Branch just before invasive changes - kind of a compromise of the >above two. > > Your thoughts? I think 1 is the best. It will minimize the port of changes between master and other branches. > Branch naming > >1. Previous - simply 2.5.0 - I think this then confuses tags and >branches that have the same name >2. As written - 2.5.0-branch - I'm liking this less. >3. Suggested by Julen stable/2.5.0 I like 3. Or perhaps release/2.5.0. I am not sure if I understand well this, and perhaps there is a very good reason. The proposal is to have a master in which development has place, and when the time comes new branches are created for each new release, so what are the tags for? I assume that won't exist branches like 2.5.0.1 and thus tags will be used. Bye > Your thoughts? > Thanks for the input > > -- > Dwayne > > *Translate* > +27 12 460 1095 > -- > Own the Future-Intel® Level Up Game Demo Contest 2013 > Rise to greatness in Intel's independent game demo contest. > Compete for recognition, cash, and the chance to get your game > on Steam. $5K grand prize plus 10 genre and skill prizes. > Submit your demo by 6/6/13. http://p.sf.net/sfu/intel_levelupd2d > ___ > Translate-pootle mailing list > Translate-pootle@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/translate-pootle -- Own the Future-Intel® Level Up Game Demo Contest 2013 Rise to greatness in Intel's independent game demo contest. Compete for recognition, cash, and the chance to get your game on Steam. $5K grand prize plus 10 genre and skill prizes. Submit your demo by 6/6/13. http://p.sf.net/sfu/intel_levelupd2d ___ Translate-pootle mailing list Translate-pootle@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/translate-pootle
[translate-pootle] Release and development process - would value your input
Hi, Julen and I met in Pretoria in January to discuss our release and development process moving forward after 2.5. I've finally managed to capture that discussion and have updated the release document here: http://docs.translatehouse.org/projects/pootle/en/latest/developers/release.html Would love you all to give that a read and check for any typos and errors. In general the doc should give some clarity on: 1. When you can contribute and land things 2. When to expect a new release of Pootle 3. What you can expect when running from master. However, we do need some input and help in these two thing: 1. When to branch when creating time-based releases. 2. What to name our branches. When to branch Options 1. As written now branch would happen at the end of the stabilising month, i.e. as late as possible - thus forcing focus on the stabalisation 2. Branch early and port change to the branch as needed - allows master to continue in rapid development 3. Branch just before invasive changes - kind of a compromise of the above two. Your thoughts? Branch naming 1. Previous - simply 2.5.0 - I think this then confuses tags and branches that have the same name 2. As written - 2.5.0-branch - I'm liking this less. 3. Suggested by Julen stable/2.5.0 Your thoughts? Thanks for the input -- Dwayne *Translate* +27 12 460 1095 -- Own the Future-Intel® Level Up Game Demo Contest 2013 Rise to greatness in Intel's independent game demo contest. Compete for recognition, cash, and the chance to get your game on Steam. $5K grand prize plus 10 genre and skill prizes. Submit your demo by 6/6/13. http://p.sf.net/sfu/intel_levelupd2d ___ Translate-pootle mailing list Translate-pootle@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/translate-pootle
