Hi,
I wonder if we should wait for June 24th before tagging the
git repository with the R_3_5_0
tag. The 3.5 release is technically ready. We won't be allowed to
push any new changes to the Mars release unless they fix an issue
that impact the entire release train. Since PDT is a leaf project,
i.e. no other project in the release train depends on PDT, it is
very unlikely that such problem would be found that requires fix in
PDT. If we find a critical issue in PDT we should provide a
solution though the PDT update sites - either through a quick 3.5.1
release or through a feature patch. Technically, both options are
post-3.5.0 effort.
Therefore,
I suggest that we tag the git repo now and continue using the
master branch for the 3.6 release. There is no reason to pile up
Gerrit patches for the next two weeks. If we need to spin a quick
3.5.1 release we can easily fork a maintenance branch from
the R_3_5_0
tag and create a Hudson job to build it.
Makes
sense?
Kaloyan
_______________________________________________
pdt-dev mailing list
pdt-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/pdt-dev