Thank you for your continued efforts. The plan makes sense to me.
Babel's release plan of two releases a year (one
in August and another one in November) was basing on the older
Eclipse Simultaneous Release (SimRel) model of a major release
in June followed by two service releases, assuming that there
are not much new strings for new functions in the service
releases. Eclipse SimRel has switched to a quarterly rolling
release model with new functions in each release. Babel's
release plan should be modified to accommodate the new strings
for new functions in the more frequent Eclipse SimRel's.
With the limited human resources our project has,
we may not be able to provide four Babel releases a year like
the Eclipse SimRel does. I'm proposing to keep producing two
Babel releases a year, but spread them out 6 months apart (one
after the June Eclipse SimRel and another one after the
December Eclipse SimRel). I also want to release Babel sooner
after the Eclipse SimRel. I'm hoping to make Babel release
available 4 weeks after the Eclipse SimRel instead of 6 weeks.
To sum up, I'm proposing to provide one Babel
release at end of July after the June Eclipse SimRel and
another Babel release at end of January after the December
Eclipse SimRel.
Any comment for the new Babel release plan
proposal?
Regards,
Kit Lo
Eclipse Babel Project Lead
IBM Eclipse SDK (IES) Technical Lead
_______________________________________________
babel-dev mailing list
babel-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/babel-dev
