[Mageia-dev] packages pushed to cauldron updates_testing before release

Wed May 30 16:41:57 CEST 2012

On Tue, 29 May 2012, David Walser wrote:
+
+> Thomas Backlund <tmb at ...> writes:
+> > 29.05.2012 19:48, David Walser skrev:
+> > > Packagers,
+> > > 
+> > > If you pushed a package to updates_testing in Cauldron before Mageia 2 was
+> > released, please make sure you re-push it if you want the fix/update included
+> > in Mageia 2.  The change should already be in the SVN, so all
+> > you need to do is resubmit it to the build system (and file a bug with an
+> > advisory and assign it to QA of course).
+> > > 
+> > 
+> > Nope.
+> > 
+> > SVN was branched according on what was tagged and uploaded on mirrors as
+> > that's the only way to make sure svn updates tree matches release tree,
+> > meaning no unwanted/unplanned changes get queued in updates tree.
+> > 
+> > So if yo want to submit anything to updates_testing, you need to commit
+> > the changes in updates tree and then submit.
+> 
+> Thomas,
+> 
+> Are you sure about that?  I had pushed taglib to updates_testing in Cauldron
+> before the release and after SVN was branched the update was already in SVN.
+> 
+> I think the branch was generated from releases/ but that includes anything that
+> was built, whether it went to release or updates_testing.
+
+Ah it seems your are right, the branch was created from the commit of
+the latest markrelease. And markrelease is also done for packages in
+cauldron updates_testing repository.
+
+