On 07/30/2014 06:47 PM, Wayne Beaton
wrote:
Can I assume that you mean Mars? ;-)
Sure, you can assume that ;)
I've started assembling the list of projects/releases that will
join Mars [0]. I'll put you down for 2.2.1 for now
Thanks.
if
you do decide to include a different release with Mars, then let
us know on this list (before the M4 deadline) and I'll update the
record.
More generally... participating projects should create a record
(if one does not already exist) for the release that they intend
to contribute in the PMI and then inform the community via this
list.
Remember that project plans need to be specified by M4. A minimal
plan that includes a description [1] of the release and a list of
issues [2] (which we can generate automatically) shouldn't be too
onerous, I hope. It would be good if you can capture a theme or
two for your plan.
SWTBot doesn't really have a plan. People come and contribute what
they want, and we release when we feel it's worth it. So I'm already
thinking about how to hack this contribution process without
planning a release. M4 is in December. Between December and June,
there can be something like 3 or 4 releases (or 0) that cannot be
planned before M4.
In the case of SWTBot, we're not much interested about the
Simultaneous Release planning, which for a small project such as
SWTBot could prevent from frequent releases if necessary. What
interest us is more to be included in Mars site and EPP package and
making sure we work well with other projects of this same Mars site.
Can the Release Train (or in that case the aggregator only) process
handle the possibility of an unexpected release after M4 ?
|