yesterday we had a discussion on IRC (mostly) about :
* 1.2.0a2 release
* versions handling in the bug tracker
Summarizing up, we decided it would be nice to release 1.2.0a2 in the
next few days.
To this end, we need to find and target appropriately all the bugs we
are willing to see fixed by this release: right now we have 3 open on
I will monitor the list, so feel free to add up bugs on that list if
you them important enough to be fixed now _and_ you are commited to
work on them...
If anything major does not show up, I'll try to publish a2 on Sunday.
The other topic we discussed is the version names to use for targeting
issues; right now we have 4 unreleased versions to target issues on:
1.1.3, 1.1.X, 1.2.0 and 1.2.0a2
The agreement was to have only one unreleased version for each branch;
since we are likely to know what will be the next stable release but
not the next development one, onsensus was we will use the full
version number (1.1.3 as of today) to target bugs on the stable branch
and 1.2.x for the development branch.
At release time:
* for the stable branch, we just create the next version
* for the development branch, we rename 1.2.x to the actual name,
then create a new 1.2.x version
I hope I did not miss any detail...
Any comment on the plan is appreciated
Get latest updates about Open Source Projects, Conferences and News.