[drupal-devel] How are patches to branches handled?
kbahey at gmail.com
Sun Feb 13 18:05:24 UTC 2005
OK, so my fears were true then.
Is there any way to get over this problem? For example, using Goba's
suggestion to tag the date/time to the build?
Maybe a better solution is to keep the first two digits the same, then
increment for every build. For example, we start at 4.5.0 with
DRUPAL-4-5 as a tag, then have some fixes, then tag with DRUPAL-4-5-1
and make a build for 4.5.1 of that module/theme, then some more fixes,
then 4.5.2, ...etc.
This means applying the same standard for core Drupal to the contrib
modules and themes.
This way, when someone says he is using 4.5.0, then all other 4.5.0
would (hopefully) experience the same issue the first guy has.
On Sun, 13 Feb 2005 12:12:50 +0100 (CET), Gerhard Killesreiter
<killesreiter at physik.uni-freiburg.de> wrote:
> On Sat, 12 Feb 2005, K B wrote:
> > On Sun, 13 Feb 2005 05:01:33 +0100, Bèr Kessels <berdrupal at tiscali.be> wrote:
> > > Op zondag 13 februari 2005 04:55, schreef K B:
> > > > What about modules, and fixes to branches?
> > > contribs do not use the last digit. I.e. a contrib like image module has
> > > nothing to do with the 4.5.1 branch, it will only have a 4.5 branch.
> > So what is the point of Scott and Goba (as examples, not to pick on
> > anyone), fixing something in 4.5?
> > Either:
> > a) the fixes gets into 4.5.0, which means we have the problem we describe,
> This is true for all contrib modules and themes.
> > b) it does not, which brings to question the value of why the fix is
> > done to the branch at all
> For the main project these patches will be available in later releases,
> ie in 4.5.3 should it ever be created.
> > c) I am missing something?
> Not anymore I hope.
More information about the drupal-devel