create a release-0.22 branch now ?
hussayn <[email protected]> Fri, 9 Jan 2009 05:00:55 -0800 (PST)
| Newsgroups | gmane.comp.java.scarab.devel |
|---|---|
| Message-ID | <[email protected]> |
Hi;
@Barry: I have read your post carefully and also i have seen the reply from
Jorge. I do second
Jorge's opinion and i think all of us would feel more comfortable with a
more sophisticated approach
to make new releases. But OTOH where is the pressure ? IMHO the pressure is
on those individuals
and companies, who effectively use Scarab and need special functionality.
There is no masterplan
that tells, what has to be done in which release. There is an ongoing (and
currently speeding up)
activity to add news stuff as needed. But i suspect, that most active
instances of Scarab would either
keep in theit current state for ever they are mature and no need to change),
or are using trunk
anyways (the more brave herarted and maybe the core developers?).
One reasonable argument to make a release once and in a while is for sanity.
SO we try to focus on
cleaning and finetuning to keep our stuff from getting into a mess.
Having said this, from the ongoing discussion it looks like we will create a
release-0.22 branch soon.
Ok, then this is my proposed TODO-List:
1.) Create the branch
http://project.tigris.org/svn/scarab/branches/releases/Scarab-0.22-RC1
2.) Modify the Scarab homepage and announce the release branch. So from now
on we will have
the stabilizing branch fro 0.22 and the ongoing development branch for
new activities.
3.) slowly but steadily work on the remaining 0.22 relevant issues.
and propagate the fixes to trunk if possible/feasible...
If during bug fixing it becomes clear, that an issue has already been
solved or obsoleted in trunk, we
should better either fix it independently in 0.22 or skip the issue, if
it turns out, that fixing would be
a time consuming task. In the latter case, we would add this to the
list of "Known issues" or in the
worst case to the list of "broken funktionality" in 0.22 (better have
this, than not tell about it at all ...)
4.) Create RC-candidates as apropriate
5.) Release
Step 1 and 2 should be a matter of 15 minutes, so we can have the release
branch this afternoon...
Or do i overloock something significant ?
regards, Hussayn
--
View this message in context: http://www.nabble.com/howto-make-a-reliable-release-0.22-tp21347530p21371854.html
Sent from the Scarab - Dev mailing list archive at Nabble.com.
------------------------------------------------------
http://scarab.tigris.org/ds/viewMessage.do?dsForumId=455&dsMessageId=1013724
To unsubscribe from this discussion, e-mail: [[email protected]].