Giuliano Colla schreef:
Mattias Gaertner ha scritto:
On Sun, 03 Jun 2007 15:31:14 +0200
Vincent Snijders <[EMAIL PROTECTED]> wrote:
Mattias Gaertner schreef:
On Sat, 02 Jun 2007 13:42:35 +0200
Giuliano Colla <[EMAIL PROTECTED]> wrote:
[...]
It would be nice if Lazarus could provide a "stable" branch, which
starts with each "official" release, and it is only maintained by
backporting bug fixes and/or "safe" small enhancements, leaving out
all the developments for next release.
[...]
Great.
[...]
I like the idea, especially because you are volunteering to do the
job.
Well, I propose the following course of action:
1) Wait some time to see if someone else volunteers (scant hopes but one
never knows :-) )
2) In the meantime determine the svn version to start with,
corresponding to the released version. Judging from dates I believe it
to be version 1810 (which is the last prior the released version date),
but positive information in place of guess would be welcome.
http://www.freepascal.org/cgi-bin/viewcvs.cgi/?root=lazarus
You could start with r10808 of trunk, since that is the revision of the
lazarus_0_9_22 tag. Maybe even better is just to copy that tagged version initially.
3) I set up a local svn repository, and create a branch (which I'd call
"stable" unless there's a better idea).
Or fixes_0_9_22, assuming that you will do the same for 0.9.24 and later
versions too.
4) With painful "diff's", or with information from developers, determine
the patches to be applied, for bugs fixed since march 27 (?), and try to
see if what comes out is a working version, or just a pitiful mess. This
phase can be useful to establish in practice the policy guidelines. I'm
in favor of a rather conservative approach, because the goal is to
provide a stable version, not all fancy nice new features, but what this
means in practice must be verified.
Logs can be helpful:
http://www.freepascal.org/cgi-bin/viewcvs.cgi/lazarus-all.log?root=logs&view=markup
Also consider looking into svnmerge as described here:
http://wiki.lazarus.freepascal.org/SVN_Migration#Merging
Hmm, while you are at the wiki, maybe put some documentation about the process there
too.
6) Decide how to proceed. Should the stable branch be accessible through
svn or should it deployed the same way as the new releases? Or should
the idea be dropped because it turned out to be unpractical?
I think it should available through svn, so that snapshot based on it can be easily
built. Creating releases based on the fixes branch doesn't seem very practical,
IMHO. Or do you want to release more frequently than we do now.
One more thing. I'm normally working with Linux, using Red Hat
Enterprise Workstation, but I run lazarus also under Fedora (currently
FC5). From what I see from the mailing list, there's no big difference
with the last releases of Mandriva or Ubuntu. I can easily test under
Windows XP, but that's all.
Currently I have no way to test under other platforms (Debian, FreeBSD
Mac OS X etc. are out of my reach).
Out of mine too. :-)
Vincent
_________________________________________________________________
To unsubscribe: mail [EMAIL PROTECTED] with
"unsubscribe" as the Subject
archives at http://www.lazarus.freepascal.org/mailarchives
