Hi,
Shouldn't we move forward ? Here is what I would suggest
- we create a release record here
http://projects.eclipse.org/projects/technology.nebula
, 1.0 sounds ok don't you think ?
- each component leader creates a theme in the project plan to
highlight what is in the release
- each component leader browse through the "Review Documentation"
tab in the release record and fill in the section Architectural
Issues / Security Issues / Non-Code Aspects / Usability / End Of
Life / Standards and Communities.
- we publish an 1.0.0RC build and create a branch in the
repository.
- we have to submit an IP log, to do so the first step would be to
go through our bugzillas and make sure the "iplog" keyword is set
on any code contribution through patch or comment so that it
appears in the generated ip log. Here is the current version :
http://www.eclipse.org/projects/ip_log.php?id=technology.nebula
- once you did your bugzilla check send a mail to the mailling
list to tell the others your part of the ip log is ok. If you need
CQ (contribution bigger than 200/250 lines) then we need to know
too.
- we pick a date
- we schedule a release review
- we tell the world about the release :)
What do you think ? Did I miss something ?
Cédric
Le 19/08/2013 18:36, Wim Jongman a écrit :